@mitu my bad

@pikey

first off, its worth noting that you need to install a driver for the ps3 controller to connect, so if you havent done that yet, i sugest you try that first, via the retropie setup.
also linux is not windows, so the fact that it works in windows, dosnt automaticly mean it also works in linux.

does the bluetooth adapter work as expected with other bluetooth devices in linux?

edit:
also, are you using an original controller?

@WildkatCT said in 4.5 Reicast BT PS3 controller setup not working correctly.:

Setting up a clean 4.5 image, can't see to get Reicast to configure controllers at all. Ran the controller setup utility, and all the button presses are detected, but in the actual emulator, only the analog stick works and the PS button is mapped to A.

Oddly though, the controller works fine when plugged in USB.

I tried manually changing the values on the .cfg file for the PS3 controller in reicast, but it doesn't seem to re-act to the changes, or at least the values I have are not corresponding to what reicast is expecting.

How can i get values that reicast would expect? Something like JS test, but those values don't seem to work.

@WildkatCT said in 4.5 Reicast BT PS3 controller setup not working correctly.:

Setting up a clean 4.5 image, can't see to get Reicast to configure controllers at all. Ran the controller setup utility, and all the button presses are detected, but in the actual emulator, only the analog stick works and the PS button is mapped to A.

Oddly though, the controller works fine when plugged in USB.

I tried manually changing the values on the .cfg file for the PS3 controller in reicast, but it doesn't seem to re-act to the changes, or at least the values I have are not corresponding to what reicast is expecting.

How can i get values that reicast would expect? Something like JS test, but those values don't seem to work.

Hello, I am experiencing this problem too, can't get any of my ps3 bt controllers to work with Reicast after the retropie 4.5 update, please help!

I have already configured the "emu.cfg" as showed below and my mappings inside the "mappings" folder are correct for my controllers.

[input] MouseSensitivity = 100 VirtualGamepadVibration = 20 device1 = 0 device1.1 = 1 device1.2 = 1 device2 = 0 device2.1 = 1 device2.2 = 1 device3 = 0 device3.1 = 1 device3.2 = 1 device4 = 0 device4.1 = 1 device4.2 = 1 maple_/dev/input/event2 = 0 maple_/dev/input/event3 = 1 maple_/dev/input/event4 = 2 maple_/dev/input/event5 = 3

Thank you @mitu , but the problem is still present.
Ich will put my experience to the other topic.

@mitu thanks.

https://retropie.org.uk/forum/topic/22312/latest-update-and-ps3-sixaxis-controller/7

Here is the link for others. Will test later.

E: Downgrading worked.

@shavecat
okay thanks

Just pair the 2nd controller as you did with the 1st one and - if they're identical - that's all. When starting a game, both controllers will be available as P1 and P2, there's nothing else to do.
If they're not identical (i.e. one is a genuine, one is a clone), you'll have to configure the 2nd controller in Emulationstation, just like you configured the first one.

@weaster007 No, I don't mean qtsixa, I mean the sixaxis driver package in the RetroPie Setup script

92b3e1df-ff2d-439a-98ba-fe0863c7fa71-image.png

'sixaxis' : Helper service to install & configure the latest drivers for official and third-party DualShock controllers (ps3controller replacement)

@Efriim Hello and welcome to the RetroPie forums.

I don't play N64 so I can't say what exactly is the best choice here, the recommendation is usually to use the standalone emulator for best performance and even so not all games are playable. In general, N64 emulation on a Pi is not ideal - other may provide better answers to this question.

The standalone pcsx_rearmed is no longer developed, use lr-pcsx_rearmed which is better supported.

It's not a bug, it's how the Sony drivers work and it's the OS/kernal that handles this. Register 'both' controllers (wired and wireless) and they should work depending on how you connect them.

There is a recent topic about Dreamcast games and their performance after the latest update - https://retropie.org.uk/forum/topic/21031. I don't use the emulator so much, so others may have a better response.

RetroPie uses whatever Raspbian's default is - so /tmp is mounted on the sdcard and not using the RAM (as most Linux PC distributions do). I assume it's because of the limited RAM memory available on such systems. RetroPie does not have any preferences here, so you can use whatever solution you like best.

Every emulator will use the GPU - directly or indirectly - otherwise they wouldn't be able to output anything on the screen :). I don't see why it shouldn't be possible to run a music player in the background, there's no limitation imposed by RetroPie - remember that the Pi image is just a Rasbpian Lite installation, almost unchanged from upstream.

We have an ongoing discussion on that in the topic about a new DS3 driver:

https://retropie.org.uk/forum/topic/15967/sony-dualshock-3-call-for-testers-sixaxis-script-module/129

You may want to give this driver a try and remap your controller in Steam Link even if it already is supported - mine was but it had digital triggers, I remapped and triggers became properly analog!

Do note that this may not work for libretro cores just because as far as I can tell, no platform emulated on RetroPie supports analog triggers (L2/R2 buttons were digital on PSX).

thanks Cyberghost. Jumped over to your suggested thread and giving that a shot.

Sorry - this became obsolete for me because of that post:
https://github.com/RetroPie/RetroPie-Setup/issues/1060

Suffering from similar issues. I will try deleting all the .uae and see if that helps me.

If no luck I plan to raise this in Github. Thanks again to @dudleydes for his efforts.

@mitu
Thank you for this tip!
The boot is faster disabling "wait for network"
and I don't have this text between splashscreen and emulation station.

So, for anybody having buggy bluetooth with 2 PS3 controllers
with a Raspberry Pi 3B+ and Retropie,
here is a solution:

disable wifi with [f4] "rfkill block wifi" disable wifi with @cyperghost 's script:
https://retropie.org.uk/forum/topic/19734/enable-disable-wifi-with-rfkill

Thanks again everyone,
we are going to have fun with my friends! :D

I just followed this guide.
https://github.com/RetroPie/RetroPie-Setup/wiki/PS3-Controller

Here are the steps I did (copied from the guide)
Navigate to the "RetroPie" icon in the Home Screen and select it using whatever key you mapped "A" to on your gamepad, and go to RetroPie Setup
Once in the RetroPie GUI, choose [Manage packages] > [driver].
Select PS3 Controller Driver ("ps3controller"), and then select [Install from source].
Once installation completes, exit RetroPie setup and return to the EmulationStation Home Screen.
Press "Start" to enter the EmulationStation Menu, and select Configure Input.
Disconnect your PS3 controller from USB. Now hold the PS button on the controller down until you see the lights on it flash sequentially. The controller should now be connected via Bluetooth.
Emulation Station should now detect another gamepad connected. Hold any button down on the controller to begin configuring it.

The part that is bolded is the part that is not working. My remote was plugged in for an hour so I know it has charge. It just flashes but doesn't actually connect at all.

@cjohnson26 I have set up a working PS3 controller for RetroPie on my PI 3B+.

It is however an original PS3 controller from purchasing the console a few years back.

The instructions from the github page you reference are not as fulsome at step 3 as they could be.

I recommend the following additional thoughts in case you haven't applied them.

3a. Reset your controller, this is a little hole on the underside of the controller that you stick an uncurled paperclip or similar into. Do not touch a button until further notice.
3b. Once the PS3controller driver is installed, you must select it to configure options.
3c. Choose your particular (compatible) controller from the list, hopefully it is there.
3d. A screen will now appear asking you to plug in the controller. Plug it in for 10 seconds, do not touch a button!
I believe at this time certain configuration files are created, including for retroarch.
3e. Unplug the controller and now press the PS button. If working, the lights will 'sweep' back and forth, rumble and settle on the controller number.

You then start ES and configure the controller.

The default setup is pretty good for retroarch emulators, although you may prefer to switch X & O!

Thank you so much, that solved it :)

@joserto86 Do you have a keyboard attached to the PI ? Please see the questions from https://retropie.org.uk/forum/topic/3/read-this-first and try to give some answers so we can better grasp your configuration.

@mitu my mistake ill ask him and thanks again